-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[teamd]: Increase wait timeout for teamd docker stop to clean Port channels. #6537
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lguohan
approved these changes
Jan 23, 2021
lguohan
changed the title
Increase wait timeout for teamd docker stop to clean Port channels.
[teamd]: Increase wait timeout for teamd docker stop to clean Port channels.
Jan 23, 2021
retest vsimage please |
@lguohan as we can see the same problem on 201911, will you consider taking the fix to 201911 as well? |
@judyjoseph and @dallan I believe this one should be cherry picked to 202012. there is no label . Can you please add? |
4 tasks
daall
pushed a commit
that referenced
this pull request
Feb 6, 2021
…annels. (#6537) The Portchannels were not getting cleaned up as the cleanup activity was taking more than 10 secs which is default docker timeout after which a SIGKILL will be send. Fixes #6199 To check if it works out for this issue in 201911 ? #6503 This issue is significantly seen in master branch compared to 201911 because the Portchannel cleanup takes more time in master. Test on a DUT with 8 Port Channels. master admin@str-s6000-acs-8:~$ time sudo systemctl stop teamd real 0m15.599s user 0m0.061s sys 0m0.038s Sonic 201911.v58 admin@str-s6000-acs-8:~$ time sudo systemctl stop teamd real 0m5.541s user 0m0.020s sys 0m0.028s
4 tasks
judyjoseph
added a commit
to judyjoseph/sonic-buildimage
that referenced
this pull request
Feb 19, 2021
abdosi
pushed a commit
that referenced
this pull request
Feb 27, 2021
The Portchannels were not getting cleaned up as the cleanup activity was taking more than 10 secs which is default docker timeout after which a SIGKILL will be send. Fix Issue #6537
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
- Why I did it
The Portchannels were not getting cleaned up as the cleanup activity was taking more than 10 secs which is default docker timeout after which a SIGKILL will be send.
Fixes #6199
To check if it works out for this issue in 201911 ? #6503
This issue is significantly seen in master branch compared to 201911 because the Portchannel cleanup takes more time in master. Test on a DUT with 8 Port Channels.
master
Sonic 201911.v58
- How I did it
Increased the timeout, by passing the timeout argument of 60sec now to container stop in case of teamd container.
- How to verify it
Checked the following cases and made sure the Portchannels are cleanup properly. Checked that in case of Warm restart of teamd, it doesn't use more time.
Case 1:
Normal stop of teamd with the fix, used teh script below to try multilple times.
Case2:
Time it takes for swss restart
Case3:
With warm restart enabled, the stop of teamd still takes around 8 secs same as before this fix.
NOTE: There is a runtime error Runtime error: ( check below logs ) which needs to be fixed. It is an existing error.
Doesn't cause any functional issue,
- Which release branch to backport (provide reason below if selected)
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)